FICO - Raghav - 2018-05-10 - WST-78 - Spec - Japan invoice summary extract (Matt by 2018-06-31) #wipdev #FIForms #abapformsfi #JapanFICO #FIOutgoingInvoices #FIAR

Specifications


WST-78-Spec-Japan invoice summary extract


Purpose

Japan invoice summary extract in csv format

Admin Info


Purpose
 Japan invoice summary extract
Requested By
 Matt
Spec Created By
 Raghav
Spec Created Date
 06/01/218
Spec QA by
 Raghav
Objects
Documant Status
 WIP

Estimates


Sl.No
 Activity
 Estimation in Hours
1
 Research
 20
2
 Documentation
 08
3
 Development/ Config
 40
4
 Unit test in DEV
 22
5
 Unit test in QUA
 10
6
 Other activity

TOTAL
 100

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]



Documents

[Attach any document(s) received for the requirement(s)]

Sample Summary Invoice.pdfJapan Summary Invoice Extract Functional Specification Document.docxJapan inv output with field mapping.xlsxExample with data.xlsx

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
 Change Details
 Requested By
 Requested On
 Notes if any

























Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

The Japan finance team will save 16 hours per month by providing the invoice to the customer via a self-service portal. Additionally, the immediate availability of invoices is expected to drive faster payment, increasing cash flow.

The Japan finance team would like to leverage a widely used SaaS offering (Infomart) to deliver invoices to their customer's electronically. This will allow our customers in Japan to have 24/7 access to their invoices, including the Summary Invoice. An ABAP program is required which will extract data from the following areas / tables:
This extract will be in CSV format, and must download to the user's machine. Once downloaded, the user will populate additional data in the required fields, save, and manually upload to the portal.

In Scope:

[List the activities to be included in scope]

Out of Scope:

[Out of scope activities]

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]




Test Plan

[List test scenarios/cases to be executed here]
Test ID
 Test Scenario
 Expected Results




Solution Details

[Provide complete technical details for configuration or programming here]



Issues

[List Issues / Bugs identified in configuration or development]